Consolidate fluentd versions#1063
Merged
Merged
Conversation
Signed-off-by: Dan Luhring <dluhring@chainguard.dev>
dlorenc
approved these changes
Jul 6, 2023
developer-guy
pushed a commit
to Dentrax/images
that referenced
this pull request
Feb 12, 2024
…1063) Signed-off-by: Dan Luhring <dluhring@chainguard.dev>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This change unifies the
:latest/:14stream with the:edge/:15stream offluentd. The current version offluentdis actually1.16.x, and1.14.xis no longer supported upstream. Meanwhile, the:15tag has actually hadv1.16.xfor the past handful of releases.In the new model, we're publishing
:latest, which tracks the latest version (again1.16.xfor the time being).To avoid an immediate breakage for end users, we're also having the
:edgetag (which we've been using to describe the most recent version) point to this same, newest-version image, so it's equivalent to:latest.To my knowledge, we currently don't have a mechanism for earmarking tags as "won't be supported after Aug 16", but let me know if there's more bookkeeping to be done here for the
:edgetag!Fixes: #582
Related: wolfi-dev/os#3389
cc: @found-it